Skip to content

CI: include answer-progress Playwright journey in production UI gate#793

Closed
BigSimmo wants to merge 7 commits into
mainfrom
cursor/answer-progress-playwright-db17
Closed

CI: include answer-progress Playwright journey in production UI gate#793
BigSimmo wants to merge 7 commits into
mainfrom
cursor/answer-progress-playwright-db17

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds the tests/answer-progress-ui-smoke.spec.ts spec to Playwright selection in playwright.config.ts so the production UI gate covers answer-progress safety assertions.
  • Updates scripts/ci-change-scope.mjs to classify edits to that spec as UI-affecting, closing a verification gap where assertion edits could slip past the required Chromium UI job.
  • Supersedes CI: include answer-progress Playwright journey in production UI gate #748 (original blocked on PR policy metadata).

Verification

  • node scripts/ci-change-scope.mjs --self-test passed.
  • node scripts/ci-change-scope.mjs --json --files tests/answer-progress-ui-smoke.spec.ts reports ui_changed: true.
  • UI verification not run: hosted CI Production UI gate required to fully validate the Playwright journey in this babysit pass.

Risk and rollout

  • Risk: low; change is limited to test and CI-classifier configuration — no runtime application behavior is altered.
  • Rollback: revert this PR; the answer-progress spec returns to the pre-CI-selection state.
  • Provider or production effects: None
Open in Web Open in Cursor 

Summary by CodeRabbit

  • Bug Fixes

    • Improved automated test selection so answer-progress and additional UI smoke tests are included in production verification.
    • Updated change detection to correctly identify answer-progress UI test changes and trigger the appropriate validation coverage.
  • Documentation

    • Added a review record documenting CI verification limitations related to unavailable external font downloads.

@supabase

supabase Bot commented Jul 17, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@cursor
cursor Bot enabled auto-merge (squash) July 17, 2026 20:36
@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Playwright production test matching now includes the answer-progress and additional UI tool specs. CI scope detection and self-tests classify the answer-progress smoke test as UI, source, and coverage scope, with the verification outcome recorded in the review ledger.

Changes

Production UI coverage

Layer / File(s) Summary
Expand production Playwright selection
playwright.config.ts
Production and top-level Playwright matching now include answer-progress-ui-smoke, tools-collapse, and tools-task-directory.
Align CI scope classification
scripts/ci-change-scope.mjs, docs/branch-review-ledger.md
The classifier allowlist and self-test recognize the answer-progress smoke test as source, coverage, and UI scope, and the verification result is recorded in the ledger.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

Suggested labels: codex

Suggested reviewers: claude

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly matches the main change: expanding the production UI gate to include the answer-progress Playwright journey.
Description check ✅ Passed The description covers Summary, Verification, and Risk and rollout, and the missing optional sections do not block understanding.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cursor/answer-progress-playwright-db17
⚔️ Resolve merge conflicts
  • Resolve merge conflict in branch cursor/answer-progress-playwright-db17

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@playwright.config.ts`:
- Around line 15-16: Update productionSpecPattern in the Playwright
configuration to include the ui-tools-collapse and ui-tools-task-directory spec
alternatives, keeping it aligned with testMatch and the production UI gate
scope.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5c2ee264-5361-4dd8-8ef8-397df0550f13

📥 Commits

Reviewing files that changed from the base of the PR and between 3fe441a and ac7098e.

📒 Files selected for processing (3)
  • docs/branch-review-ledger.md
  • playwright.config.ts
  • scripts/ci-change-scope.mjs

Comment thread playwright.config.ts
Comment on lines +15 to 16
/.*(?:answer-progress-ui-smoke|ui-(smoke|stress|accessibility|tools|overlap|universal-search|specifiers|formulation|pwa))\.spec\.ts/;
const mockupSpecPattern = /.*ui-(tools|tools-collapse|tools-task-directory)\.spec\.ts/;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Keep the production matcher aligned with testMatch.

Line 15 still omits ui-tools-collapse and ui-tools-task-directory, although Line 22 and the PR objective include both. If the Chromium production project uses productionSpecPattern, those specs will remain excluded from the production UI gate. Add both alternatives here or explicitly remove them from the production-scope objective.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@playwright.config.ts` around lines 15 - 16, Update productionSpecPattern in
the Playwright configuration to include the ui-tools-collapse and
ui-tools-task-directory spec alternatives, keeping it aligned with testMatch and
the production UI gate scope.

@github-actions

Copy link
Copy Markdown

CI triage

CI failed on this PR. Automated classification of the 2 failed job(s):

  • Production UIneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
  • PR requiredneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #3107 (cancelled).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants